Adding the AVATAR_GRAVATAR_FIELD setting #82
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 3 commits
December 20, 2015 20:30
|
Just pulled all new changes, we'll see if the build goes well. |
|
Build passes, merge that up! |
grantmcconnaughey
added a commit
that referenced
this pull request
Dec 21, 2015
Adding the AVATAR_GRAVATAR_FIELD setting
|
Merged up! BOOOOOM. Thanks, @Toogy |
|
Yay thanks @grantmcconnaughey 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adding AVATAR_GRAVATAR_FIELD setting to allow developers to define their own user field where the gravatar email is retrieved.
It defaults to 'email', so the behavior will stay the same as currently.
When changed to something like 'gravatar', django-avatar tries to get the avatar in
user.gravatar.This is useful when we want to separate email and gravatar in a project.